Quantum Entanglement Communication Service

ABSTRACT

A quantum entanglement communication service can be provided by detecting a request to access data stored at a first computer. In response to detecting the data access request, a request can be generated to request that a server computer generate an entangled particle pair. Measurement data can be received, the measurement data corresponding to a measurement observed after interacting a first bit of a token stored at a second computer with a first entangled particle from the entangled particle pair. An operation to perform on a second entangled particle of the entangled particle pair at the first computer can be determined and performed. A state of the second entangled particle can be measured to obtain a value, and a bit string can be generated, where the bit string can include a number that corresponds to the value.

BACKGROUND

In some communications networks, sensitive and ultra-sensitive data canbe stored for use by various devices and/or users. Malicious actors maybe able to observe communications in and/or through some communicationsnetworks to intercept such sensitive and/or ultra-sensitive data and/orto gain access to such data. Even some multi-factor authenticationtechnologies cannot stop certain attackers with access to acommunication link and/or a computer involved in a trusted communicationchannel. Thus, some malicious actors may observe communications ofsensitive and ultra-sensitive data and/or may access such data withoutbeing properly authenticated.

SUMMARY

The present disclosure is directed to a quantum entanglementcommunication service. A first device (e.g., a receiving device) canrequest data from a second device (e.g., a transmitting device). In someembodiments, for example, the receiving device can send a data accessrequest to the transmitting device. The data access request can be usedto request data that can be stored at the transmitting device. The data,however, may be sensitive data and the transmitting device may requireauthentication to receive the data. According to embodiments of theconcepts and technologies disclosed herein, the receiving device canstore a token having a number of bits.

The transmitting device may know the number of bits included in thetoken, in some embodiments. In some other embodiments, the data accessrequest may specify the number of bits in the token. The transmittingdevice can generate a request. The request can request that a servercomputer (e.g., via execution of a quantum entanglement communicationservice) generate an entangled particle pair for each bit of the token.The request also can specify endpoints for a communication session orlink in or over which the data can be shared. The server computer cangenerate the requested entangled particle pairs that can includeentangled particles. According to various embodiments of the conceptsand technologies disclosed herein, the phrase “entangled particles” asused, illustrated, and/or described herein, can be used to refer tophotons in an Einstein-Podolsky-Rosen (“EPR”) entangled state, Bellstate particles, or the like. The server computer can provide, to thetransmitting device, one particle from each entangled particle pair. Theserver computer also can provide, to the receiving device, the otherentangled particles from each entangled particle pair. The transmittingdevice and the receiving device can store the entangled particles inorder, if more than one entangled particle is received.

In response to receiving the entangled particles, the receiving devicecan begin the authentication using quantum entanglement as illustratedand described herein. The receiving device can select a first bit of thetoken and a first entangled particle. The receiving device can interactthe first bit of the token with the first entangled particle, e.g., viaa controlled NOT (“CNOT”) gate, followed by putting the token bit into asuperposition state via a Hadamard gate, and measure the system. Thereceiving device can generate measurement data, e.g., by measuring thetoken bit and the entangled particle, where the measurement data cancapture the observed or measured state of the system, which can be onevalue of 00, 01, 10, or 11. The receiving device can send themeasurement data to the transmitting device. The transmitting device canselect a first entangled particle and determine an operation to performon the first entangled particle based on the measurement data.

Namely, if the measurement data indicates that the measurement 00 wasobserved (e.g., measured) at the receiving device, the transmittingdevice may take no action on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 01 was observed(e.g., measured) at the receiving device, the transmitting device mayperform an X gate operation on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 10 was observed(e.g., measured) at the receiving device, the transmitting device mayperform a Z gate operation on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 11 was observed(e.g., measured) at the receiving device, the transmitting device mayperform an X gate operation and a Z gate operation on its correspondingentangled particle.

The transmitting device can perform the determined operation on theentangled particle and measure the state of the entangled particle. Themeasured state may be a value of either 0 or 1. The transmitting devicecan store the state as the first bit of the token. As long as additionalbits of the token remain, these operations by the receiving device andthe transmitting device may be repeated until the transmitting device orthe receiving device determines that no additional bits of the tokenremain to be transmitted. When no more bits of the token remain, thetransmitting device can be in possession of a bit string that can matchthe token. The bit string can be communicated to an authenticationservice to authenticate the receiving device (e.g., using the bitstring). If authentication is successful, the transmitting device canprovide the data to the receiving device.

According to one aspect of the concepts and technologies disclosedherein, a system is disclosed. The system can include a first computerhaving a processor and a memory as well as a quantum processor capableof performing a quantum algorithm and quantum memory capable of storingquantum state. The memory can store computer-executable instructionsthat, when executed by the processor, cause the processor to performoperations whether classical or quantum instructions. The operations caninclude detecting, at the first computer, a data access request toaccess data stored at the first computer; and in response to detectingthe data access request, generating, by the first computer, a requestincluding a request that a server computer generate an entangledparticle pair.

The server computer can include an entangled particle pair generator.The operations further can include receiving, by the first computer,measurement data that corresponds to a measurement observed afterinteracting a first bit of a token stored at a second computer with afirst entangled particle from the entangled particle pair; determining,by the first computer, an operation to perform on a second entangledparticle of the entangled particle pair at the first computer;performing, by the first computer, the operation on the second entangledparticle; measuring, at the first computer, a state of the secondentangled particle, the state including a value; and generating, by thefirst computer, a bit string including a number that corresponds to thevalue.

In some embodiments, the measurement can include a value of 00, and theoperation on the second entangled particle can include measuring thestate of the second particle. In some embodiments, the measurement caninclude a value of 01, and the operation on the second entangledparticle can include performing an X gate operation on the secondentangled particle. In some embodiments, the measurement can include avalue of 10, and the operation on the second entangled particle caninclude performing a Z gate operation on the second entangled particle.In some embodiments, the measurement can include a value of 11, and theoperation on the second entangled particle can include performing an Xgate operation and a Z gate operation on the second entangled particle.

In some embodiments, the request specifies endpoints of a communicationlink over which the data is to be transmitted. The endpoints can includethe first computer and the second computer. The server computer can sendthe second entangled particle to the second computer. In someembodiments, the computer-executable instructions, when executed by theprocessor, cause the processor to perform operations that further caninclude determining if the token can include another bit, and inresponse to determining that the token can include the other bit:receiving another instance of measurement data, where the other instanceof measurement data can include another measurement observed afterinteracting a second bit of the token with a third entangled particlefrom another entangled particle pair; obtaining a fourth entangledparticle; determining another operation to perform on the fourthentangled particle based on the other value; performing the operation onthe fourth entangled particle; measuring a state of the fourth entangledparticle, the state including another value; and adding another numberthat corresponds to the other value to the bit string. In someembodiments, the first computer can include entangled particle isolationand measurement hardware.

According to another aspect of the concepts and technologies disclosedherein, a method is disclosed. The method can include detecting, at afirst computer including a processor, a data access request to accessdata stored at the first computer; in response to detecting the dataaccess request, generating, by the processor, a request including arequest that a server computer generate an entangled particle pair,where the server computer can include an entangled particle pairgenerator; receiving, by the processor, measurement data thatcorresponds to a measurement observed after interacting a first bit of atoken stored at a second computer with a first entangled particle fromthe entangled particle pair; determining, by the processor, an operationto perform on a second entangled particle of the entangled particle pairat the first computer; performing, by the processor, the operation onthe second entangled particle; measuring, at the first computer, a stateof the second entangled particle, the state including a value; andgenerating, by the processor, a bit string including a number thatcorresponds to the value.

In some embodiments, the measurement can include a value of 00, and theoperation on the second entangled particle can include measuring thestate of the second particle. In some embodiments, the measurement caninclude a value of 01, and the operation on the second entangledparticle can include performing an X gate operation on the secondentangled particle. In some embodiments, the measurement can include avalue of 10, and the operation on the second entangled particle caninclude performing a Z gate operation on the second entangled particle.In some embodiments, the measurement can include a value of 11, and theoperation on the second entangled particle can include performing an Xgate operation and a Z gate operation on the second entangled particle.

In some embodiments, the request specifies a number of bits in thetoken, and the request for generation of an entangled particle pair caninclude a request to generate the number of entangled particle pairs. Insome embodiments, the request specifies endpoints of a communicationlink over which the data is to be transmitted. The endpoints can includethe first computer and the second computer. The server computer can sendthe second entangled particle to the second computer.

In some embodiments, the method further can include determining, by theprocessor, if the token can include another bit, and in response todetermining that the token can include the other bit: receiving anotherinstance of measurement data, wherein the other instance of measurementdata can include another measurement observed after interacting a secondbit of the token with a third entangled particle from another entangledparticle pair; obtaining a fourth entangled particle; determininganother operation to perform on the fourth entangled particle based onthe other value; performing the operation on the fourth entangledparticle; measuring a state of the fourth entangled particle, the stateincluding another value; and adding another number that corresponds tothe other value to the bit string. In some embodiments, the firstcomputer can include entangled particle isolation and measurementhardware.

According to yet another aspect of the concepts and technologiesdisclosed herein, a computer storage medium is disclosed. The computerstorage medium can store computer-executable instructions that, whenexecuted by a processor, cause the processor to perform operations. Theoperations can include detecting, at the first computer, a data accessrequest to access data stored at the first computer; and in response todetecting the data access request, generating, by the first computer, arequest including a request that a server computer generate an entangledparticle pair. The server computer can include an entangled particlepair generator. The operations further can include receiving, by thefirst computer, measurement data that corresponds to a measurementobserved after interacting a first bit of a token stored at a secondcomputer with a first entangled particle from the entangled particlepair; determining, by the first computer, an operation to perform on asecond entangled particle of the entangled particle pair at the firstcomputer; performing, by the first computer, the operation on the secondentangled particle; measuring, at the first computer, a state of thesecond entangled particle, the state including a value; and generating,by the first computer, a bit string including a number that correspondsto the value.

In some embodiments, the request specifies endpoints of a communicationlink over which the data is to be transmitted, wherein the endpointsinclude the first computer and the second computer, and wherein theserver computer sends the second entangled particle to the secondcomputer. In some embodiments, the computer-executable instructions,when executed by the processor, can cause the processor to performoperations that further can include determining if the token can includeanother bit, and in response to determining that the token can includethe other bit: receiving another instance of measurement data, whereinthe other instance of measurement data can include another measurementobserved after interacting a second bit of the token with a thirdentangled particle from another entangled particle pair; obtaining afourth entangled particle; determining another operation to perform onthe fourth entangled particle based on the other value; performing theoperation on the fourth entangled particle; measuring a state of thefourth entangled particle, the state including another value; and addinganother number that corresponds to the other value to the bit string.

Other systems, methods, and/or computer program products according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, and be within thescope of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram illustrating an illustrative operatingenvironment for various embodiments of the concepts and technologiesdescribed herein.

FIG. 2 is a flow diagram showing aspects of a method for authenticatinga receiving device using a token and entangled particles, according toan illustrative embodiment of the concepts and technologies describedherein.

FIG. 3 is a flow diagram showing aspects of a method for transmittingdata using a quantum entanglement communication link, according to anillustrative embodiment of the concepts and technologies describedherein.

FIG. 4 is a flow diagram showing aspects of a method for receiving datausing a quantum entanglement communication link, according to anillustrative embodiment of the concepts and technologies describedherein.

FIG. 5 schematically illustrates a network, according to an illustrativeembodiment of the concepts and technologies described herein.

FIG. 6 is a block diagram illustrating an example computer systemconfigured to provide a quantum entanglement communication service,according to some illustrative embodiments of the concepts andtechnologies described herein.

FIG. 7 is a block diagram illustrating an example mobile deviceconfigured to interact with a quantum entanglement communicationservice, according to some illustrative embodiments of the concepts andtechnologies described herein.

FIG. 8 is a diagram illustrating a computing environment capable ofimplementing aspects of the concepts and technologies disclosed herein,according to some illustrative embodiments of the concepts andtechnologies described herein.

DETAILED DESCRIPTION

The following detailed description is directed to a quantum entanglementcommunication service. A first device (e.g., a receiving device) canrequest data from a second device (e.g., a transmitting device). In someembodiments, for example, the receiving device can send a data accessrequest to the transmitting device. The data access request can be usedto request data that can be stored at the transmitting device. The data,however, may be sensitive data and the transmitting device may requireauthentication to receive the data. According to embodiments of theconcepts and technologies disclosed herein, the receiving device canstore a token having a number of bits.

The transmitting device may know the number of bits included in thetoken, in some embodiments. In some other embodiments, the data accessrequest may specify the number of bits in the token. The transmittingdevice can generate a request. The request can request that a servercomputer (e.g., via execution of a quantum entanglement communicationservice) generate an entangled particle pair for each bit of the token.The request also can specify endpoints for a communication session orlink in or over which the data can be shared. The server computer cangenerate the requested entangled particle pairs that can includeentangled particles. According to various embodiments of the conceptsand technologies disclosed herein, the phrase “entangled particles” asused, illustrated, and/or described herein, can be used to refer tophotons in an EPR entangled state, Bell state particles, or the like.The server computer can provide, to the transmitting device, oneparticle from each entangled particle pair. The server computer also canprovide, to the receiving device, the other entangled particles fromeach entangled particle pair. The transmitting device and the receivingdevice can store the entangled particles in order, if more than oneentangled particle is received.

In response to receiving the entangled particles, the receiving devicecan begin the authentication using quantum entanglement as illustratedand described herein. The receiving device can select a first bit of thetoken and a first entangled particle. The receiving device can interactthe first bit of the token with the first entangled particle, e.g., viaa CNOT gate, followed by putting the token bit into a superpositionstate via a Hadamard gate, and measure the system. The receiving devicecan generate measurement data, e.g., by measuring the token bit and theentangled particle, where the measurement data can capture the observedor measured state of the system, which can be one value of 00, 01, 10,or 11. The receiving device can send the measurement data to thetransmitting device. The transmitting device can select a firstentangled particle and determine an operation to perform on the firstentangled particle based on the measurement data.

Namely, if the measurement data indicates that the measurement 00 wasobserved (e.g., measured) at the receiving device, the transmittingdevice may take no action on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 01 was observed(e.g., measured) at the receiving device, the transmitting device mayperform an X gate operation on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 10 was observed(e.g., measured) at the receiving device, the transmitting device mayperform a Z gate operation on its corresponding entangled particle. Ifthe measurement data indicates that the measurement 11 was observed(e.g., measured) at the receiving device, the transmitting device mayperform an X gate operation and a Z gate operation on its correspondingentangled particle.

The transmitting device can perform the determined operation on theentangled particle and measure the state of the entangled particle. Themeasured state may be a value of either 0 or 1. The transmitting devicecan store the state as the first bit of the token. As long as additionalbits of the token remain, these operations by the receiving device andthe transmitting device may be repeated until the transmitting device orthe receiving device determines that no additional bits of the tokenremain to be transmitted. When no more bits of the token remain, thetransmitting device can be in possession of a bit string that can matchthe token. The bit string can be communicated to an authenticationservice to authenticate the receiving device (e.g., using the bitstring). If authentication is successful, the transmitting device canprovide the data to the receiving device.

While the subject matter described herein is presented in the generalcontext of program modules that execute in conjunction with theexecution of an operating system and application programs on a computersystem, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, and other types of structures that performparticular tasks or implement particular abstract data types. Moreover,those skilled in the art will appreciate that the subject matterdescribed herein may be practiced with other computer systemconfigurations, including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like.

Referring now to FIG. 1, aspects of an operating environment 100 forvarious embodiments of the concepts and technologies disclosed hereinfor a quantum entanglement communication service will be described,according to an illustrative embodiment. The operating environment 100shown in FIG. 1 includes a server computer 102. The server computer 102can operate in communication with and/or as part of a communicationsnetwork (“network”) 104, though this is not necessarily the case.

According to various embodiments, the functionality of the servercomputer 102 may be provided by various computing devices including, butnot limited to, one or more server computers, desktop computers, laptopcomputers, application servers, other computing systems, and the like.It should be understood that the functionality of the server computer102 can be provided by a single device, by two or more similar devices,and/or by two or more dissimilar devices. For purposes of describing theconcepts and technologies disclosed herein, the server computer 102 isdescribed herein as a server computer. It should be understood that thisembodiment is illustrative, and should not be construed as beinglimiting in any way.

The server computer 102 can execute an operating system (not labeled inFIG. 1) and one or more application programs such as, for example, aquantum entanglement communication service 106. The operating system caninclude a computer program for controlling the operation of the servercomputer 102. The quantum entanglement communication service 106 caninclude an executable program that can be configured to execute on topof the operating system to provide various functions as illustrated anddescribed herein. Prior to describing the functionality of the quantumentanglement communication service 106 in more detail, some of the otherentities of the operating environment 100 will be disclosed to aid indescribing the functionality of the quantum entanglement communicationservice 106.

As shown in FIG. 1, the server computer 102 also can include anentangled particle generator 108 (labeled “entangled particle generator108” in FIG. 1). The entangled particle generator 108 can be configuredto generate an entangled particle pair 110. The entangled particle pair110 can include a first entangled particle 112A and a second entangledparticle 112B. According to various embodiments, the quantumentanglement communication service 106 can be configured to control theentangled particle generator 108. Thus, it can be appreciated thequantum entanglement communication service 106 can trigger the entangledparticle generator 108 to generate one or more entangled particle pairs110 on demand (e.g., in response to the quantum entanglementcommunication service 106 receiving a request 114 from a device such asthe transmitting device 116 illustrated in FIG. 1), or at other times aswill be illustrated and described herein.

As is generally understood, quantum entanglement of two entangledparticles 112A, 112B can be broken simply by observing or measuring oneof the entangled particles 112A, 112B. Similarly, the quantumentanglement of two entangled particles 112A, 112B can be broken by anyinteraction between an entangled particle 112, 112B and its environment.Furthermore, a measurement of an entangled particle 112A will be randomwithout additional information, so a measurement without knowing more isuseless. Finally, because quantum state cannot be cloned (provablyforbidden by quantum mechanics), the entangled particles 112A, 112B andtheir observed states are impossible to observe, measure, or clonewithout destroying the quantum entanglement between the entangledparticles 112A, 112B. These and other features of entangled particles112A, 112B are used by embodiments of the concepts and technologiesdisclosed herein to provide access to certain types of informationand/or devices.

As shown in FIG. 1, the operating environment 100 also can include areceiving device 120. The receiving device 120 can also execute thequantum entanglement communication application 118 (e.g., the receivingdevice 120 can also store instructions that can correspond to aninstance of an embodiment of the quantum entanglement communicationapplication 118 illustrated and described herein). Via execution ofrespective instances of the quantum entanglement communicationapplication 118, the transmitting device 116 and the receiving device120 can communicate in a secure fashion as will be illustrated anddescribed herein.

The transmitting device 116 and the receiving device 120 can alsoinclude an instance of entangled particle isolation and measurementhardware 122 (labeled “EP I & M HW 122” in FIG. 1). The entangledparticle isolation and measurement hardware 122 can include an isolationchamber or other hardware for isolating entangled particles such as theentangled particle 112A and the entangled particle 112B. In someembodiments of the concepts and technologies disclosed herein, theentangled particle isolation and measurement hardware 122 can include,for example, a quantum memory. The entangled particle isolation andmeasurement hardware 122 also can include hardware for measuring a stateof the entangled particles 112A, 112B; systems including the entangledparticles 112A, 112B; and the like. The entangled particle isolation andmeasurement hardware 122 also can include a quantum processor, Hadamardgates, and/or other hardware.

According to various embodiments of the concepts and technologiesdisclosed herein, the receiving device 120 also can store a token 124,which in various embodiments can be stored via traditional and/orclassical memory technologies. The token 124 can include any bit stringof one bit or more, though tokens 124 often can include tens, hundred,thousands, or even millions of bits. The token 124 can be obtained bythe receiving device 120 in various manners, as generally is understood.In the illustrated embodiment, the operating environment 100 also caninclude an authentication service 126. The authentication service 126can correspond to an authentication server, a certificate authority, orthe like. In the illustrated embodiment, the authentication service 126can include a certificate authority that can issue a certificate or thetoken 124 to the receiving device 120, and also can includefunctionality for performing an authentication function as will beillustrated and described herein.

For purposes of simplifying the description of the concepts andtechnologies disclosed herein, an example token 124 having a bit lengthof eight bits is illustrated in FIG. 1. Of course, this is merely asimplified example and should not be construed as being limiting in anyway. Furthermore, because authentication and the issuance ofcertificates and/or tokens 124 can be performed in a variety of mannersby a variety of devices and/or entities, it should be understood thatthese examples are illustrative, and therefore should not be construedas being limiting in any way. Now that the elements of the operatingenvironment 100 have been introduced, the functionality of the quantumentanglement communication service 106 and the quantum entanglementcommunication application 118 will now be described in additionaldetail.

According to various embodiments of the concepts and technologiesdisclosed herein, the transmitting device 116 and the receiving device120 can be configured to establish a communications link with eachother. The communications link can be established via any desired mediaincluding, but not limited to, wired communications technologies,wireless technologies, and the like. Thus, it should be understood thatthe communications link can be established via the network 104, in someembodiments and/or other networks as illustrated and described herein.In some embodiments, the communications link can be established afterthe transmitting device 116 and/or the receiving device 120 authenticatewith each other and/or the server computer 102. According to variousembodiments of the concepts and technologies disclosed herein, however,the communications link between the transmitting device 116 and thereceiving device 120 need not be a secure channel, as will be explainedin more detail below. It should be understood that this example isillustrative, and therefore should not be construed as being limiting inany way.

As shown in FIG. 1, the transmitting device 116 can possess data 128,and the receiving device 120 can attempt to access or obtain the data128, for example via generating a data access request 130 (labeled “dataaccess request 130” in FIG. 1). The data 128 can be any information inany format including files, streaming data, etc., that the transmittingdevice 116 is to transmit and/or provide to the receiving device 120.According to various embodiments, however, the data 128 can be sensitivedata that will only be provided to properly authenticating entities. Insome embodiments, the data 128 can correspond to super-sensitive data,and therefore may only be provided to the receiving device 120 if thereceiving device 120 can authenticate as illustrated and describedherein.

In particular, the quantum entanglement communication application 118executed by the transmitting device 116 can be configured to useentangled particles 112A, 112B to determine if the receiving device 120should be able to access the data 128. As will be appreciated withreference to the embodiments of the concepts and technologies disclosedherein, the use of quantum entanglement to grant or deny access canprevent observers or other unauthorized entities from interceptingauthentication information and/or otherwise gaining unauthorized accessto the data 128. It should be understood that this example isillustrative, and therefore should not be construed as being limiting inany way.

According to various embodiments of the concepts and technologiesdisclosed herein, the transmitting device 116 (e.g., via execution ofthe quantum entanglement communication application 118) can beconfigured to generate a request 114. According to various embodimentsof the concepts and technologies disclosed herein, the request 114generated by the transmitting device 116 can specify two endpoints anumber of bits in the token 124. It should be clarified that while thetransmitting device 116 does not possess a copy of the token 124, thetransmitting device 116 can be aware of the number of bits in the token124 in some embodiments. In some other embodiments, the receiving device120 can inform the transmitting device 116 of the number of bits in thetoken 124 when requesting access to the transmitting device (e.g., byincluding the number of bits in the data access request 130 illustratedand described herein).

According to some embodiments, the endpoints identified in the request114 will include the transmitting device 116 and a device that is toreceive the data 128 if authenticated. In the illustrated embodiment ofFIG. 1, the endpoints will include the transmitting device 116 and thereceiving device 120. Either or both of the endpoints can be identifiedby one or more device identifiers (e.g., an international mobilesubscriber identity (“IMSI”), an international mobile equipment identity(“IMEI”), a subscriber permanent identity (“SUPI”), a media accesscontrol identifier (“MAC ID”), etc.), network identifiers (e.g., an IPaddress, a network ID, etc.), user information (e.g., accountinformation, user ID, etc.), or other identifiers.

The request 114 can be sent to the server computer 102 to request thatthe quantum entanglement communication service 106 generate an entangledparticle pair 110. The server computer 102 can be configured to analyzethe request 114 to determine the endpoints, which will correspond toentities that will receive the entangled particles 112A, 112B. In someembodiments of the concepts and technologies disclosed herein, thetransmitting device 116 can be configured to generate a request 114 foran entangled particle pair 110 for each bit of the token 124 (e.g., theoperations for generating the request 114 can be iterated for each bitof the token 124).

In some other embodiments, the request 114 can specify the number ofbits in the token 124, and the server computer 102 can be configured togenerate a corresponding number of entangled particle pairs 110 (e.g.,if the token 124 has eight bits, the server computer 102 can beconfigured to generate eight entangled particle pairs 110; if the token124 has one hundred bits, the server computer 102 can be configured togenerate one hundred entangled particle pairs 110; etc.). In yet otherembodiments, the first request 114 for an entangled particle pair 110can be generated by the transmitting device 116, and the receivingdevice 120 can generate subsequent requests 114 for entangled particlepairs 110 (e.g., a new request 114 can be made by the receiving device120 for each bit of the token 124 that is to be used to authenticatewith the transmitting device 116). Thus, it can be appreciated that insome embodiments, the transmitting device 116 does not need to know thenumber of bits in the token 124. It should be understood that thisexample is illustrative, and therefore should not be construed as beinglimiting in any way.

The server computer 102 (e.g., via execution of the quantum entanglementcommunication service 106) can be configured to generate one or moreentangled particle pairs 110, and to provide one or more entangledparticles 112A from the entangled particle pairs 110 to the transmittingdevice 116, and to provide the other (second) entangled particles 112Bfrom the entangled particle pairs 110 to the receiving device 120. As isgenerally understood, the entangled particles 112A, 112B from theentangled particle pair 110 can be entangled, and therefore operationsperformed on one of the entangled particles 112A may result in a changeto the entangled particle 112B, subject to various requirements ofquantum mechanics.

In the embodiment shown in FIG. 1, the server computer 102 can generateeight entangled particle pairs 110, and then can send eight entangledparticles 112A to the transmitting device 116 and eight entangledparticles 112B to the receiving device 120. As noted above, oneentangled particle pair 110 can be generated at a time in someembodiments, so this is merely an illustrative embodiment and should notbe construed as being limiting in any way.

The transmitting device 116 can be configured (e.g., via execution ofthe quantum entanglement communication application 118) to receive theentangled particles 112A and to store the entangled particles 112A usingthe entangled particle isolation and measurement hardware 122. Theentangled particle isolation and measurement hardware 122 can beconfigured to isolate the entangled particles 112A from externalobservation and/or interactions, and to store the entangled particles112A in order, if more than one entangled particle 112A is provided atone time. Similarly, the receiving device 120 can be configured toreceive the one or more entangled particle 112B and to store theentangled particles 112B using the entangled particle isolation andmeasurement hardware 122. The entangled particle isolation andmeasurement hardware 122 can be configured to isolate the entangledparticle 112B from external observation and/or interactions, and tostore the entangled particles 112B in order, if more than one entangledparticle 112B is provided at one time.

In some embodiments, though not illustrated in FIG. 1, the transmittingdevice 116 can be configured (e.g., via execution of the quantumentanglement communication application 118), to generate a challenge orother response to the data access request 130. Such a challenge orresponse, if generated, can be sent to the receiving device 120 and canprompt the receiving device 120 to begin providing the token 124 asillustrated and described herein. In some other embodiments, thechallenge can be omitted, and receipt of the one or more entangledparticles 112B by the receiving device 120 can cause the receivingdevice 120 to begin providing information representing the token 124 asillustrated and described herein. It should be understood that theseexamples are illustrative, and therefore should not be construed asbeing limiting in any way.

The receiving device 120 can be configured (e.g., via execution of thequantum entanglement communication application 118) to beginauthentication with the transmitting device 116 in response to receivingthe entangled particles 112B. In particular, the receiving device 120can be configured to identify a first bit of the token 124. Thereceiving device 120 also can be configured to select a first entangledparticle 112B, if more than one entangled particle 112B is provided atone time, or to use the entangled particle 112B if only one entangledparticle 112B is provided at one time. For purposes of simplifying thedescription of the concepts and technologies disclosed herein, theembodiment where multiple entangled particles 112B are received at onetime will be described as an example embodiment. It should be understoodthat this example is illustrative, and therefore should not be construedas being limiting in any way.

The receiving device 120 can be configured to interact the first bit ofthe token (in the illustrated embodiment a “0”) with the first entangledparticle 112B, and to measure the system after the interaction. In onecontemplated embodiment, for example, the receiving device 120 caninteract the first bit of the token with the first entangled particle112B (e.g., via a CNOT gate), and can put the token bit into asuperposition state via a Hadamard gate, and then measure the system.The receiving device 120 can be configured (e.g., via execution of thequantum entanglement communication application 118) to generatemeasurement data 132. The measurement data 132 can describe the observedmeasurement of the entangled particle 112B as observed at the receivingdevice 120 after interacting the bit of the token 124 with the entangledparticle. It can be appreciated that the measurement will be in the formof two bits, and will have a value of 00, 01, 10, or 11. The receivingdevice 120 can generate the measurement data 132 and send themeasurement data 132 to the transmitting device 116.

It can be appreciated that measurement or observation of the entangledparticle 112B at the receiving device 120 will destroy the entangledsystem of the token bit and the receivers half of the entangled particlepair 110, but the observed state can be used as will be illustrated anddescribed herein. It should be noted, however, that for each bit of thetoken 124, the transmitting device 116 or the receiving device 120 canbe configured to generate the request 114; to receive entangledparticles 112A, 112B; to store the entangled particle 112A, 112B; tointeract one of the entangled particles 112A, 112B with a bit from thetoken 124; to generate and/or receive the measurement data 132; and/orother operations as illustrated and described herein.

As such, the concepts and technologies disclosed herein may appear to beinefficient and counterintuitive. Embodiments of the concepts andtechnologies disclosed herein, however, can result in the ability totransmit information corresponding to the token 124 that is imperviousto unauthorized access and/or observation, since the token 124 itself isnever transmitted and since interception of the measurement data 132will be useless to any entity not in possession of the other entangledparticle 112A. It should be understood that this example isillustrative, and therefore should not be construed as being limiting inany way.

The transmitting device 116 can be configured (e.g., via execution ofthe quantum entanglement communication application 118), to receive themeasurement data 132. As noted above, the measurement data 132 candescribe the measurement of the measurement of the entangled particle112B at the receiving device 120 with a bit of the token 124, andtherefore can have one of four measurements, 00, 01, 10, or 11. Based onthe observed measurement at the receiving device 120, the transmittingdevice 116 can be configured to perform an operation on the entangledparticle 112A to determine the corresponding bit of the token 124.

In particular, if the measurement data 132 indicates that themeasurement 00 was observed (e.g., measured) at the receiving device120, the transmitting device 116 may be configured to take no action onits corresponding entangled particle 112A (e.g., the first entangledparticle 112A in a first iteration of this process), and to measure thestate of the entangled particle 112A. The measured state of theentangled particle will be a 0 or a 1, and the measured state cancorrespond to the first bit of the token 124. Similarly, if themeasurement data 132 indicates that the measurement 01 was observed(e.g., measured) at the receiving device 120, the transmitting device116 can be configured to perform an X gate operation on itscorresponding entangled particle 112A (e.g., the first entangledparticle 112A in a first iteration of this process), and then measurethe state of the entangled particle 112A. The measured state of theentangled particle can be a 0 or a 1, and the measured state cancorrespond to the first bit of the token 124.

If the measurement data 132 indicates that the measurement 10 wasobserved (e.g., measured) at the receiving device 120, the transmittingdevice 116 can be configured to perform a Z gate operation on itscorresponding entangled particle 112A (e.g., the first entangledparticle 112A in a first iteration of this process), and then canmeasure the state of the entangled particle 112A. The measured state ofthe entangled particle can be a 0 or a 1, and the measured state cancorrespond to the first bit of the token 124. Finally, if themeasurement data 132 indicates that the measurement 11 was observed(e.g., measured) at the receiving device 120, the transmitting device116 can be configured to perform an X gate operation and a Z gateoperation on its corresponding entangled particle 112A (e.g., the firstentangled particle 112A in a first iteration of this process), and thencan measure the state of the entangled particle 112A. The measured stateof the entangled particle can be a 0 or a 1, and the measured state cancorrespond to the first bit of the token 124.

Thus, it can be appreciated that the embodiments of the concepts andtechnologies disclosed herein can effectively transmit the first bit ofthe token 124 by way of the entangled particles 112A, 112B and themeasurement data 132. In other words, the first bit of the token 124 canbe communicated by the receiving device 120 to the transmitting device116 without actually transmitting the bit, but rather by communicatingthe measurement data 132 and using the entangled particles 112A, 112B.It should be understood that this example is illustrative, and thereforeshould not be construed as being limiting in any way.

According to various embodiments of the concepts and technologiesdisclosed herein, after the first instance of measurement data 132 istransmitted (e.g., corresponding to the first bit of the token 124), thetransmitting device 116 or the receiving device can determine ifadditional bits of the token 124 remain. If so, the transmitting device116 or the receiving device 120 can be configured to generate a request114 (for another entangled particle pair 110 if only one entangledparticle pair 110 is generated initially), or the receiving device 120can select a next entangled particle 112B (if multiple are provided atone time). The receiving device 120 can repeat the operationsillustrated and described above (e.g., select a next bit of the token124, interact the next bit of the token 124 with the next entangledparticle 112B, measure the state of the system, and send measurementdata 132 to the transmitting device 116).

Similarly, the transmitting device 116 can repeat its operations,namely, receive the measurement data 132, select or receive a nextentangled particle 112A, perform an operation on the entangled particle112A (if the measurement data is anything other than 00), measure thestate of the entangled particle 112A after the operation, and record theobserved measure as the next bit of a bit string. Thus, it can beappreciated that the above operations can be repeated by thetransmitting device 116 and the receiving device 120 until each bit ofthe token 124 has been represented at the transmitting device 116. Thus,when the receiving device 120 and the transmitting device 116 haveperformed the above operations until no more bits remain in the token124 at the receiving device 120, the transmitting device 116 will be inpossession of a bit string that can represent, in order, each of thebits of the token 124.

According to some embodiments of the concepts and technologies disclosedherein, the receiving device 120 and the transmitting device 116 can beconfigured to communicate with each other regarding the communication ofthe token 124. For example, if the receiving device 120 and/or thetransmitting device 116 detects an inadvertent operation or observationthat was made of an entangled particle 112A, 112B, the receiving device120 and/or the transmitting device 116 can be configured to request oneor more new entangled particle pairs 110. Similarly, the receivingdevice 120 and/or the transmitting device 116 can be configured toinstruct the other device (e.g., the receiving device 120 and/or thetransmitting device 116) to disregard the corresponding entangledparticle 112A, 112B of the inadvertently operated on and/or observedentangled particle 112A, 112B. Other error correction processes can beperformed in accordance with various embodiment of the concepts andtechnologies disclosed herein. As such, it should be understood thatthis example is illustrative, and therefore should not be construed asbeing limiting in any way.

Thus, it can be appreciated that the transmitting device 116 can beconfigured to assemble the determined bits into a bit string. The bitstring can be essentially identical to the token 124. Thus, embodimentsof the concepts and technologies disclosed herein can be used to enablethe transmitting device 116 to essentially recreate the token 124 at thetransmitting device 116. Thus, it can be appreciated that embodiments ofthe concepts and technologies disclosed herein can be used to “transfer”the token 124 from the receiving device 120 to the transmitting device116 without actually transferring the token 124 itself and/or bitsthereof. Rather, the transmitting device 116 can generate the token 124(or a bit string corresponding thereto) at the transmitting device 116based on the bits represented by the state of the entangled particles112A. It should be understood that this example is illustrative, andtherefore should not be construed as being limiting in any way.

Once the bit string (which, as noted above can match the token 124) isin possession of the transmitting device 116, the transmitting device116 can provide the bit string to the authentication service 126. Itshould be understood that the box having dashed lines and labeled “token124” at the transmitting device 116 in FIG. 1 can correspond to the bitstring (and not actually the token 124). The authentication service 126can determine if the receiving device 120 is to be authenticated or not;and to issue an authentication decision to the transmitting device 116.If the receiving device 120 is authenticated, the transmitting device116 can send the data 128 to the receiving device 120. If the receivingdevice 120 is not authenticated, the transmitting device 116 can blockor deny transmission of the data 128 to the receiving device 120. Itshould be understood that these examples are illustrative, and thereforeshould not be construed as being limiting in any way.

In practice, a receiving device 120 can request data from a transmittingdevice 116. In some embodiments, for example, the receiving device 120can send a data access request 130 to the transmitting device 116. Thedata access request 130 can be used to request data 128 that is storedat the transmitting device 116. The data 128, however, may be sensitivedata and the transmitting device 116 may require authentication toreceive the data 128.

According to embodiments of the concepts and technologies disclosedherein, the receiving device 120 can store a token 124 having a numberof bits. The transmitting device 116 may know the number of bits, insome embodiments, or the data access request 130 may specify the numberof bits of the token 124. In some other embodiments, the transmittingdevice 116 may not know the number of bits included in the token 124.The transmitting device 116 can generate a request 114. The request 114can request that a server computer 102 (e.g., via execution of a quantumentanglement communication service 106) generate an entangled particlepair 110 for each bit of the token 124. The request 114 also can specifyendpoints for a communication session or link in or over which the data128 will be shared. The server computer 102 can generate the requestedentangled particle pairs 110 that include entangled particles 112A,112B. The server computer 102 can provide, to the transmitting device116, the entangled particles 112A. The server computer 102 also canprovide, to the receiving device 120, the entangled particles 112B. Thetransmitting device 116 and the receiving device 120 can store theentangled particles 112A, 112B in order.

In response to receiving the entangled particles 112B, the receivingdevice 120 can begin the authentication using quantum entanglement asillustrated and described herein. The receiving device 120 can select afirst bit of the token 124 and a first entangled particle 112B. Thereceiving device 120 can interact the first bit of the token 124 withthe first entangled particle 112B, and measure the system. The receivingdevice 120 can generate measurement data that captures the observed ormeasured state of the system, which can be one value of 00, 01, 10, or11. The receiving device 120 can send the measurement data 132 to thetransmitting device 116.

The transmitting device 116 can select a first entangled particle 112A,and determine an operation to perform on the first entangled particle112A based on the measurement data 132. Namely, if the measurement data132 indicates that the measurement 00 was observed (e.g., measured) atthe receiving device 120, the transmitting device 116 can be configuredto take no action on its corresponding entangled particle 112A. If themeasurement data 132 indicates that the measurement 01 was observed(e.g., measured) at the receiving device 120, the transmitting device116 can be configured to perform an X gate operation on itscorresponding entangled particle 112A. If the measurement data 132indicates that the measurement 10 was observed (e.g., measured) at thereceiving device 120, the transmitting device 116 can be configured toperform a Z gate operation on its corresponding entangled particle 112A.If the measurement data 132 indicates that the measurement 11 wasobserved (e.g., measured) at the receiving device 120, the transmittingdevice 116 can be configured to perform an X gate operation and a Z gateoperation on its corresponding entangled particle 112A. The transmittingdevice 116 can be configured to perform the determined operation on theentangled particle 112A and to measure the state of the entangledparticle 112A. The state measured by the transmitting device 116 can bea value of either 0 or 1.

The transmitting device 116 can be configured to store the state as thefirst bit of the token 124. As long as additional bits of the token 124remain, these operations by the receiving device 120 and thetransmitting device 116 can be repeated until the transmitting device116 or the receiving device 120 determines that no additional bits ofthe token 124 remain to be represented. When no more bits of the token124 remain, the transmitting device 116 can be in possession of a bitstring that can match the token 124, and can communicate the bit stringto an authentication service 126 to authenticate the receiving device120. If authentication is successful, the transmitting device 116 canprovide the data 128 to the receiving device 120. If the authenticationis not successful, the transmitting device 116 may elect not to providethe data 128 to the receiving device 120.

It should be understood that the phrases “transmitting device” and“receiving device” are merely illustrative of one example embodiment,and refer to the transmitting of and/or receiving of the data 128. Insome embodiments, the transmitting device 116 can correspond to a secureserver, and the receiving device 120 can correspond to a gateway thatmaintains an only existing communication channel with the secure server.Because other devices can use the concepts and technologies disclosedherein, it should be understood that these examples are illustrative,and therefore should not be construed as being limiting in any way.

FIG. 1 illustrates one server computer 102, one network 104, onetransmitting device 116, one receiving device 120, and oneauthentication service 126. It should be understood, however, thatvarious implementations of the operating environment 100 can include oneor more than one server computer 102, one or more than one network 104,one or more than one transmitting device 116, one or more than onereceiving device 120, and zero, one, or more than one authenticationservice 126. As such, the illustrated embodiment should be understood asbeing illustrative, and should not be construed as being limiting in anyway.

Turning now to FIG. 2, aspects of a method 200 for enabling a quantumentanglement communication link between two devices will be described indetail, according to an illustrative embodiment. It should be understoodthat the operations of the methods disclosed herein are not necessarilypresented in any particular order and that performance of some or all ofthe operations in an alternative order(s) is possible and iscontemplated. The operations have been presented in the demonstratedorder for ease of description and illustration. Operations may be added,omitted, and/or performed simultaneously, without departing from thescope of the concepts and technologies disclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used herein,is used expansively to include routines, applications, applicationmodules, program modules, programs, components, data structures,algorithms, and the like. Computer-readable instructions can beimplemented on various system configurations including single-processoror multiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof. As used herein, the phrase “cause aprocessor to perform operations” and variants thereof is used to referto causing a processor of a computing system or device, such as theserver computer 102, the transmitting device 116, and/or the receivingdevice 120, to perform one or more operations and/or causing theprocessor to direct other components of the computing system or deviceto perform one or more of the operations.

For purposes of illustrating and describing the concepts of the presentdisclosure, the method 200 is described herein as being performed by theserver computer 102 via execution of one or more software modules suchas, for example, the quantum entanglement communication service 106. Itshould be understood that additional and/or alternative devices and/ornetwork nodes can provide the functionality described herein viaexecution of one or more modules, applications, and/or other softwareincluding, but not limited to, the quantum entanglement communicationservice 106. Thus, the illustrated embodiments are illustrative, andshould not be viewed as being limiting in any way.

The method 200 begins at operation 202. At operation 202, the servercomputer 102 can receive a request 114 for an entangled particle pair110 from a transmitting device 116. As explained above, the request 114can be generated by a transmitting device 116 for each bit of a token124 that is to be “transmitted,” or more accurately “communicated” tothe transmitting device 116 from the receiving device 120 according toembodiments of the concepts and technologies disclosed herein. Asexplained above, the request 114 generated in operation 202 can, in someembodiments, specify a number of entangled particle pairs 110 togenerate and/or a number of bits in the token 124, which can be the samenumber. In some other embodiments, a new request 114 can be generatedfor each bit in the token 124. As such, the illustrated embodiment isillustrative and should not be construed as being limiting in any way.

From operation 202, the method 200 can proceed to operation 204. Atoperation 204, the server computer 102 can determine the endpoints forthe communications link associated with the request 114 received inoperation 202, as well as a number of bits in a token 124 associatedwith the request 114. As explained above, the request 114 can specify,in some embodiments, the transmitting device 116 and the receivingdevice 120, which can be identified by one or more device identifiers(e.g., an IMSI, an IMEI, a SUFI, a MAC ID, etc.), network identifiers(e.g., an IP address, a network ID, etc.), user information (e.g.,account information, user ID, etc.), or other identifiers. Similarly,the request 114 can specify a number of bits in the token 124, which maybe known to the transmitting device 116 and/or the receiving device 120.Thus, operation 204 can correspond to the server computer 102determining, from the request 114 or information associated with therequest 114, the transmitting device 116 and the receiving device 120and a number of bits in the token 124. Because the transmitting device116 and the receiving device 120 can be determined in additional and/oralternative manners, and because the number of bits in the token 124 canalso be determined in additional and/or alternative manners, it shouldbe understood that these examples are illustrative, and therefore shouldnot be construed as being limiting in any way.

From operation 204, the method 200 can proceed to operation 206. Atoperation 206, the server computer 102 can generate an entangledparticle pair 110 per bit of the token 124. According to variousembodiments of the concepts and technologies disclosed herein, theserver computer 102 can trigger generation of a number of entangledparticle pairs 110, where the number can correspond to a number of bitsin the token 124. As explained above, the server computer 102 caninclude an entangled particle generator 108, so operation 206 cancorrespond to the server computer 102 triggering generation of the oneor more entangled particle pairs 110 by the entangled particle generator108. It should be understood that this example is illustrative, andtherefore should not be construed as being limiting in any way.

From operation 206, the method 200 can proceed to operation 208. Atoperation 208, the server computer 102 can send the entangled particles112A from the entangled particle pairs 110 to the transmitting device116. From operation 208, the method 200 can proceed to operation 210. Atoperation 210, the server computer 102 can send the other entangledparticles 112B from the entangled particle pairs 110 to the receivingdevice 120.

As such, it can be appreciated that the server computer 102 can beentirely unaware of the token 124, the data 128, and/or any single bitcorresponding to the token 124 and/or the data 128 when the entangledparticle pairs 110 are generated. As such, the server computer 102 canhandle communication of the entangled particles 112A, 112B without anyknowledge of the token 124, the data 128, and/or bits thereof, which insome implementations can enhance security of the embodiments of theconcepts and technologies disclosed herein. It should be understood thatthis example is illustrative, and therefore should not be construed asbeing limiting in any way.

From operation 210, the method 200 can proceed to operation 212. Themethod 200 can end at operation 212.

Turning now to FIG. 3, aspects of a method 300 for authenticating areceiving device 120 using a token 124 and entangled particles 112A,112B will be described in detail, according to an illustrativeembodiment. For purposes of illustrating and describing the concepts ofthe present disclosure, the method 300 is described herein as beingperformed by the transmitting device 116 via execution of one or moresoftware modules such as, for example, the quantum entanglementcommunication application 118. It should be understood that additionaland/or alternative devices and/or network nodes can provide thefunctionality described herein via execution of one or more modules,applications, and/or other software including, but not limited to, thequantum entanglement communication application 118. Thus, theillustrated embodiments are illustrative, and should not be viewed asbeing limiting in any way.

Although not separately shown in FIG. 3, it should be understood thatthe transmitting device 116 can be configured to establish acommunications link with the receiving device 120 at one or more ofvarious times in the method flow illustrated in FIG. 3. It should beunderstood that the establishment of the communications link can occurat any time before transmission of the measurement data 132 occurs. Assuch, it can be appreciated that the communications link can beestablished before operation 302, before operation 316, and/or at othertimes. Furthermore, it should be understood that the communications linkcan persist during the communications between the transmitting device116 and the receiving device 120, or that the communications link can beestablished and release each time the measurement data 132 istransmitted. It should be understood that these examples areillustrative, and therefore should not be construed as being limiting inany way.

The method 300 can begin at operation 302. At operation 302, thetransmitting device 116 can detect a request for the data 128 stored atthe transmitting device 116. In some embodiments, for example, thetransmitting device 116 can receive the data access request 130 from thereceiving device 120. Because the request for the data 128 can bereceived in additional and/or alternative manners, it should beunderstood that this example is illustrative, and therefore should notbe construed as being limiting in any way.

From operation 302, the method 300 can proceed to operation 304. Atoperation 304, the transmitting device 116 can generate a request forone or more entangled particle pairs 110. In some embodiments, therequest generated in operation 304 can correspond to the request 114illustrated and described herein. Thus, it can be understood thatoperation 304 (or other operation) can also include the transmittingdevice 116 determining a number of bits in the token 124 that will beused by the receiving device 120 to authenticate with the transmittingdevice 116 (in order to obtain the data 128). In some embodiments, asnoted above, the request 114 can identify endpoints associated with therequest 114.

In the example illustrated in FIG. 1, the endpoints can correspond tothe transmitting device 116 and the receiving device 120. In someembodiments, the data access request 130 can identify the number of bitsin the token 124. In some other embodiments, the request 114 does notindicate the number of bits in the token 124, as explained above. Forsimplicity, the embodiment wherein the number of bits of the token 124is known will be described. In light of the above, however, it should beunderstood that this example is illustrative, and therefore should notbe construed as being limiting in any way.

From operation 304, the method 300 can proceed to operation 306. Atoperation 306, the transmitting device 116 can receive one or moreentangled particles 112A from the server computer 102. Operation 306also can include the transmitting device 116 isolating the entangledparticles 112A to ensure that the entanglement between the entangledparticles 112A and the entangled particles 112B is maintained. Inparticular, as is generally known, any measurement and/or observation ofthe entangled particles 112A can break the entanglement between theentangled particles 112A and the entangled particles 112B, so theentangled particles 112A can be isolated from measurement and/orobservation of the entangled particles 112A. The entangled particles112A can be stored in order by the transmitting device 116, as explainedabove. It should be understood that this example is illustrative, andtherefore should not be construed as being limiting in any way.

From operation 306, the method 300 can proceed to operation 308. Atoperation 308, the transmitting device 116 can receive measurement data132 from the receiving device 120. As noted above, the measurement data132 can indicate a measurement observed at the receiving device 120after interacting with an entangled particle 112B with a bit of thetoken 124. Thus, the measurement data 132 can indicate the measurementas 00, 01, 10, or 11. It should be understood that this example isillustrative, and therefore should not be construed as being limiting inany way.

From operation 308, the method 300 can proceed to operation 310. Atoperation 310, the transmitting device 116 can select a next (or firstin the first iteration of operation 310) entangled particle 112A. Asnoted above, the entangled particles 112A can be stored by thetransmitting device 116 in order, in some embodiments, and therefore canbe selected in order by the transmitting device 116. It should beunderstood that this example is illustrative, and therefore should notbe construed as being limiting in any way.

From operation 310, the method 300 can proceed to operation 312. Atoperation 312, the transmitting device 116 can perform an operation onthe selected entangled particle 112A. It can be appreciated thatoperation 312 also can include the transmitting device 116 determiningthe operation to perform on the entangled particle 112A. In particular,if the measurement data 132 indicates that the measurement 00 wasobserved (e.g., measured) at the receiving device 120, the transmittingdevice 116 can be configured to take no action on its correspondingentangled particle 112A. If the measurement data 132 indicates that themeasurement 01 was observed (e.g., measured) at the receiving device120, the transmitting device 116 can be configured to perform an X gateoperation on its corresponding entangled particle 112A. If themeasurement data 132 indicates that the measurement 10 was observed(e.g., measured) at the receiving device 120, the transmitting device116 can be configured to perform a Z gate operation on its correspondingentangled particle 112A. If the measurement data 132 indicates that themeasurement 11 was observed (e.g., measured) at the receiving device120, the transmitting device 116 can be configured to perform an X gateoperation and a Z gate operation on its corresponding entangled particle112A. Thus, operation 312 can include determining the operation toperform on the entangled particle 112A, as well as performing theoperation on the entangled particle 112A. It should be understood thatthis example is illustrative, and therefore should not be construed asbeing limiting in any way.

From operation 312, the method 300 can proceed to operation 314. Atoperation 314, the transmitting device 116 can measure the state of theentangled particle 112A after the operation in operation 312 isperformed on the entangled particle 112A (or after no operation isperformed in the case of a 00 measurement at the receiving device 120 asnoted above). The measured state of the entangled particle can be a 0 ora 1, as explained above.

From operation 314, the method 300 can proceed to operation 316. Atoperation 316, the transmitting device 116 can determine a correspondingbit of the token 124. The value of the bit of the token 124 will be themeasured state of the entangled particle 112A, and therefore will be a 0or a 1.

From operation 316, the method 300 can proceed to operation 318. Atoperation 316, the transmitting device 116 can determine if the token124 includes another bit (e.g., if any additional bits of the token 124remain to be represented). As noted above, the transmitting device 116can be aware of the number of bits in the token 124, in someembodiments. In some other embodiments, the transmitting device 116 candetermine the number of bits of the token 124 based on the data accessrequest 130. In yet other embodiments, the transmitting device 116 maydetermine that additional bits of the token 124 remain if anotherinstance of measurement data 132 is received. Because the determinationof operation 318 as to whether additional bits of the token 124 remaincan be made in additional and/or alternative manners, it should beunderstood that these examples are illustrative, and therefore shouldnot be construed as being limiting in any way.

If the transmitting device 116 determines, in any iteration of operation318, that the token 124 includes another bit (e.g., if any additionalbits of the token 124 remain to be represented), the method 300 canreturn to operation 308, where another instance of measurement data 132can be received. Operations 308-318 can be iterated until thetransmitting device 116 determines, in any iteration of operation 318,that the token 124 does not include another bit (e.g., that noadditional bits of the token 124 remain to be represented).

If the transmitting device 116 determines, in any iteration of operation318, that the token 124 does not include another bit (e.g., that noadditional bits of the token 124 remain to be represented), the method300 can proceed to operation 320. At operation 320, the transmittingdevice 116 can compile, construct, or assemble the bits determined inthe one or more iterations of operation 316, and can output a bitstring. In some embodiments, the transmitting device 116 can provide thebit string to the authentication service 126. It can be appreciated thatthe bit string compiled in operation 320 can be identical to the token124 stored at the receiving device 120, as the bits of the bit stringand the token 124 can be identical. Thus, FIG. 1 shows the token 124existing on the transmitting device 116, but it can be appreciated fromthe illustrated and described embodiments herein that the token 124 isnot actually transmitted from the receiving device 120 to thetransmitting device 116. Rather, as noted above, the box labeled “token124” at the transmitting device 116 can correspond to the bit string. Itshould be understood that this example is illustrative, and thereforeshould not be construed as being limiting in any way.

From operation 320, the method 300 can proceed to operation 322. Atoperation 322, the transmitting device 116 can determine if theauthentication service 126 has authenticated the bit string thatcorresponds to the token 124. It can be appreciated that theauthentication service 126 can issue an authentication decision in anynumber of manners such as, for example, a yes/no decision; a true/falsedecision; a allow/deny decision; and/or other binary and/or non-binarydecisions. Because the determination of operation 322 as to whetherauthentication has been successful can be made in additional and/oralternative manners, it should be understood that the illustratedembodiment is illustrative and should not be construed as being limitingin any way.

If the transmitting device 116 determines, in operation 322, that theauthentication service 126 has authenticated the bit string thatcorresponds to the token 124, the method 300 can return to operation324. In operation 324, the transmitting device 116 can transmit the data128 to the receiving device 120. Thus, it can be appreciated that thereceiving device 120 will have authenticated with the transmittingdevice 116 using a token 124, without ever transmitting even one bit ofthe token 124 to the transmitting device 116. It should be understoodthat this example is illustrative, and therefore should not be construedas being limiting in any way.

If the transmitting device 116 determines, in operation 322, that theauthentication service 126 has not authenticated the bit string thatcorresponds to the token 124, the method 300 can return to operation326. In operation 326, the transmitting device 116 can block or denyaccess to the data 128 by the receiving device 120. Thus, it can beappreciated that the receiving device 120 will have failed toauthenticate with the transmitting device 116 using a token 124, withoutever transmitting even one bit of the token 124 to the transmittingdevice 116. The receiving device may again request the data and theattempt to authenticate can be iterated, if desired. It should beunderstood that this example is illustrative, and therefore should notbe construed as being limiting in any way.

From operation 326, the method 300 can proceed to operation 328. Themethod 300 also can proceed to operation 328 from operation 324. Themethod 300 can end at operation 328.

Turning now to FIG. 4, aspects of a method 400 for authenticating with atransmitting device using a token and entangled particles will bedescribed in detail, according to an illustrative embodiment. Forpurposes of illustrating and describing the concepts of the presentdisclosure, the method 400 is described herein as being performed by thereceiving device 120 via execution of one or more software modules suchas, for example, the quantum entanglement communication application 118.It should be understood that additional and/or alternative devicesand/or network nodes can provide the functionality described herein viaexecution of one or more modules, applications, and/or other softwareincluding, but not limited to, the quantum entanglement communicationapplication 118. Thus, the illustrated embodiments are illustrative, andshould not be viewed as being limiting in any way.

The method 400 begins at operation 402. At operation 402, the receivingdevice 120 can request data 128 from a transmitting device 116. Invarious embodiments of the concepts and technologies disclosed herein,the receiving device 120 can perform the functionality of operation 402by generating a data access request 130. As noted above, the data 128can be any information in any format including files, streaming data,etc., that the transmitting device 116 is to transmit and/or provide tothe receiving device 120. According to various embodiments, however, thedata 128 can be sensitive or even super-sensitive data that will only beprovided to properly authenticating entities. Because the concepts andtechnologies disclosed herein can be used to authenticate devices forany type of data, however, it should be understood that this example isillustrative, and therefore should not be construed as being limiting inany way.

From operation 402, the method 400 can proceed to operation 404. Atoperation 404, the receiving device 120 can receive one or moreentangled particles 112B from the server computer 102. Operation 406also can include the receiving device 120 isolating the entangledparticles 112B to ensure that the entanglement between the entangledparticles 112B and the entangled particles 112A is maintained asexplained herein. If more than one entangled particle 112B is receivedin operation 404, the more than one entangled particles 112B can bestored in order by the receiving device 120, as explained above. Itshould be understood that this example is illustrative, and thereforeshould not be construed as being limiting in any way.

From operation 404, the method 400 can proceed to operation 406. Atoperation 406, the receiving device 120 can select a next (or first ifthe first iteration of operation 406) bit of the token 124 stored at thereceiving device 120. In the example shown in FIG. 1, a first bit of thetoken 124 can be a 0, a second bit of the token can be a 1, etc. Itshould be understood that this example is illustrative, and thereforeshould not be construed as being limiting in any way.

From operation 406, the method 400 can proceed to operation 408. Atoperation 408, the receiving device 120 can select a next (or first ifthe first iteration of operation 408) entangled particle 112B. As notedabove, the entangled particles 112B can be stored by the receivingdevice 120 in order, in some embodiments, and therefore can be selectedin order by the receiving device 120. It should be understood that thisexample is illustrative, and therefore should not be construed as beinglimiting in any way.

From operation 408, the method 400 can proceed to operation 410. Atoperation 410, the receiving device 120 can interact the selected bit ofthe token 124 with the selected entangled particle 112B. From operation410, the method 400 can proceed to operation 412. At operation 412, thereceiving device 120 can measure a state of the system existing afterinteracting the selected bit of the token 124 with the selectedentangled particle 112B. As noted above, the measurement observed inoperation 412 can have two bits (since one bit of the token 124 having avalue of 0 or 1 was interacted with an entangled particle 112B, themeasurement of which would have a single state value of 0 or 1). Thus,the state measured in operation 412 will be one of 00, 01, 10, or 11.This state can be measured by the receiving device 120 in operation 412.

From operation 412, the method 400 can proceed to operation 414. Atoperation 414, the receiving device 120 can generate and transmitmeasurement data 132 to the transmitting device 116. As explainedherein, the measurement data 132 can indicate a value of 00, 01, 10, or11. In some embodiments, the measurement data 132 also can indicate ifadditional bits of the token 124 remain. Thus, operation 414 can includethe receiving device 120 generating the measurement data 132 and sendingthe measurement data 132 to the transmitting device 116. It should beunderstood that the measurement data 132 must be transmitted no fasterthan the speed of light, and that the measurement data must betransmitted to the transmitting device 116 to maintain consistency withthe laws of quantum mechanics. It should be understood that this exampleis illustrative, and therefore should not be construed as being limitingin any way.

From operation 414, the method 400 can proceed to operation 416. Atoperation 414, the receiving device 120 can determine if the token 124includes another bit (e.g., if any additional bits of the token 124remain to be represented). As noted above, the receiving device 120 canstore the token 124 and therefore be aware of the number of bits in thetoken 124, in some embodiments. Because the determination of operation416 as to whether additional bits of the token 124 remain can be made inadditional and/or alternative manners, it should be understood thatthese examples are illustrative, and therefore should not be construedas being limiting in any way.

If the receiving device 120 determines, in any iteration of operation416, that the token 124 includes another bit (e.g., if any additionalbits of the token 124 remain to be represented), the method 400 canreturn to operation 406, where a next bit of the token 124 can beselected. Operations 406-416 can be iterated until the receiving device120 determines, in any iteration of operation 416, that the token 124does not include another bit (e.g., that no additional bits of the token124 remain to be represented).

If the receiving device 120 determines, in any iteration of operation416, that the token 124 does not include another bit (e.g., that noadditional bits of the token 124 remain to be represented), the method400 can proceed to operation 418. At operation 418, the receiving device120 can receive the data 128 (e.g., the data requested in operation402). It should be understood that a pause may occur between operations416 and 418 (e.g., while the transmitting device 116 authenticates thebit string generated at the transmitting device 116 and then transmitsthe data 128 to the receiving device 120). It should be understood thatthis example is illustrative, and therefore should not be construed asbeing limiting in any way.

From operation 418, the method 400 can proceed to operation 420. Themethod 400 can end at operation 420.

Turning now to FIG. 5, additional details of the network 104 areillustrated, according to an illustrative embodiment. The network 104includes a cellular network 502, a packet data network 504, for example,the Internet, and a circuit switched network 506, for example, apublicly switched telephone network (“PSTN”). The cellular network 502includes various components such as, but not limited to, basetransceiver stations (“BTSs”), Node-B's or e-Node-B's, base stationcontrollers (“BSCs”), radio network controllers (“RNCs”), mobileswitching centers (“MSCs”), mobile management entities (“MMEs”), shortmessage service centers (“SMSCs”), multimedia messaging service centers(“MMSCs”), home location registers (“HLRs”), home subscriber servers(“HSSs”), visitor location registers (“VLRs”), charging platforms,billing platforms, voicemail platforms, GPRS core network components,location service nodes, an IP Multimedia Subsystem (“IMS”), and thelike. The cellular network 502 also includes radios and nodes forreceiving and transmitting voice, data, and combinations thereof to andfrom radio transceivers, networks, the packet data network 504, and thecircuit switched network 506.

A mobile communications device 508, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 502. The cellular network502 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 502 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSDPA), and HSPA+. The cellular network502 also is compatible with 4G, 4.5G, and 5G mobile communicationsstandards as well as evolved and future mobile standards.

The packet data network 504 includes various devices, for example,servers, computers, databases, and other devices in communication withone another, as is generally known. The packet data network 504 devicesare accessible via one or more network links. The servers often storevarious files that are provided to a requesting device such as, forexample, a computer, a terminal, a smartphone, or the like. Typically,the requesting device includes software (a “browser”) for executing aweb page in a format readable by the browser or other software. Otherfiles and/or data may be accessible via “links” in the retrieved files,as is generally known. In some embodiments, the packet data network 504includes or is in communication with the Internet. The circuit switchednetwork 506 includes various hardware and software for providing circuitswitched communications. The circuit switched network 506 may include,or may be, what is often referred to as a plain old telephone system(POTS). The functionality of a circuit switched network 506 or othercircuit-switched network are generally known and will not be describedherein in detail.

The illustrated cellular network 502 is shown in communication with thepacket data network 504 and a circuit switched network 506, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 510, for example, a PC, a laptop, a portabledevice, or another suitable device, can communicate with one or morecellular networks 502, and devices connected thereto, through the packetdata network 504. It also should be appreciated that theInternet-capable device 510 can communicate with the packet data network504 through the circuit switched network 506, the cellular network 502,and/or via other networks (not illustrated).

As illustrated, a communications device 512, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 506, and therethrough to the packetdata network 504 and/or the cellular network 502. It should beappreciated that the communications device 512 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 510. In the specification, the network 104 isused to refer broadly to any combination of the networks 502, 504, 506.It should be appreciated that substantially all of the functionalitydescribed with reference to the network 104 can be performed by thecellular network 502, the packet data network 504, and/or the circuitswitched network 506, alone or in combination with other networks,network elements, and the like.

FIG. 6 is a block diagram illustrating a computer system 600 configuredto provide the functionality described herein for providing a quantumentanglement communication service, in accordance with variousembodiments of the concepts and technologies disclosed herein. Thus, theserver computer 102, the transmitting device 116, the receiving device120, and/or a device that hosts the authentication service 126 can havean architecture similar or even identical to the computer system 600.The computer system 600 includes a processing unit 602, a memory 604,one or more user interface devices 606, one or more input/output (“I/O”)devices 608, and one or more network devices 610, each of which isoperatively connected to a system bus 612. The bus 612 enablesbi-directional communication between the processing unit 602, the memory604, the user interface devices 606, the I/O devices 608, and thenetwork devices 610.

The processing unit 602 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. As used herein,the word “processor” and/or the phrase “processing unit” when used withregard to any architecture or system can include multiple processors orprocessing units distributed across and/or operating in parallel in asingle machine or in multiple machines. Furthermore, processors and/orprocessing units can be used to support virtual processing environments.Processors and processing units also can include state machines,application-specific integrated circuits (“ASICs”), combinationsthereof, or the like. Because processors and/or processing units aregenerally known, the processors and processing units disclosed hereinwill not be described in further detail herein.

The memory 604 communicates with the processing unit 602 via the systembus 612. In some embodiments, the memory 604 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 602 via the system bus 612. The memory 604 includes anoperating system 614 and one or more program modules 616. The operatingsystem 614 can include, but is not limited to, members of the WINDOWS,WINDOWS CE, and/or WINDOWS MOBILE families of operating systems fromMICROSOFT CORPORATION, the LINUX family of operating systems, theSYMBIAN family of operating systems from SYMBIAN LIMITED, the BREWfamily of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS,and/or LEOPARD families of operating systems from APPLE CORPORATION, theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems, and the like.

The program modules 616 may include various software and/or programmodules described herein. In some embodiments, for example, the programmodules 616 include the quantum entanglement communication service 106,the quantum entanglement communication application 118, and/or theauthentication service 126. These and/or other programs can be embodiedin computer-readable media containing instructions that, when executedby the processing unit 602, perform one or more of the methods 200, 300,and/or 400 described in detail above with respect to FIGS. 2-4 and/orother functionality as illustrated and described herein. It can beappreciated that, at least by virtue of the instructions embodying themethods 200, 300, and/or 400, and/or other functionality illustrated anddescribed herein being stored in the memory 604 and/or accessed and/orexecuted by the processing unit 602, the computer system 600 is aspecial-purpose computing system that can facilitate providing thefunctionality illustrated and described herein. According toembodiments, the program modules 616 may be embodied in hardware,software, firmware, or any combination thereof. Although not shown inFIG. 6, it should be understood that the memory 604 also can beconfigured to store the request 114, the token 124, the data 128, thedata access request 130, the measurement data 132, and/or other data, ifdesired.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 600. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes only non-transitory embodiments ofcomputer readable media as illustrated and described herein. Thus,computer storage media can include volatile and non-volatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer-readable instructions, datastructures, program modules, or other data. Computer storage mediaincludes, but is not limited to, RAM, ROM, Erasable Programmable ROM(“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flashmemory or other solid state memory technology, CD-ROM, digital versatiledisks (“DVD”), or other optical storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store the desired information andwhich can be accessed by the computer system 600. In the claims, thephrase “computer storage medium” and variations thereof does not includewaves or signals per se and/or communication media.

The user interface devices 606 may include one or more devices withwhich a user accesses the computer system 600. The user interfacedevices 606 may include, but are not limited to, computers, servers,personal digital assistants, cellular phones, or any suitable computingdevices. The I/O devices 608 enable a user to interface with the programmodules 616. In one embodiment, the I/O devices 608 are operativelyconnected to an I/O controller (not shown) that enables communicationwith the processing unit 602 via the system bus 612. The I/O devices 608may include one or more input devices, such as, but not limited to, akeyboard, a mouse, or an electronic stylus. Further, the I/O devices 608may include one or more output devices, such as, but not limited to, adisplay screen or a printer.

The network devices 610 enable the computer system 600 to communicatewith other networks or remote systems via a network, such as the network104. Examples of the network devices 610 include, but are not limitedto, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, atelephonic interface, a bridge, a router, or a network card. The network104 may include a wireless network such as, but not limited to, aWireless Local Area Network (“WLAN”) such as a WI-FI network, a WirelessWide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”)such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such aWiMAX network, or a cellular network. Alternatively, the network 104 maybe a wired network such as, but not limited to, a Wide Area Network(“WAN”) such as the Internet, a Local Area Network (“LAN”) such as theEthernet, a wired Personal Area Network (“PAN”), or a wired MetropolitanArea Network (“MAN”).

As shown in FIG. 6, the computer system 600 also can include theentangled particle isolation and measurement hardware 122 illustratedand described herein. As such, it should be understood that the computersystem 600 can include a quantum memory, a quantum processor, Hadamardgates, and/or other hardware as illustrated and described herein. Assuch, it can be appreciated that the computer system 600 can function asthe transmitting device 116 and/or the receiving device 120 in someembodiments. It should be understood that this example is illustrative,and therefore should not be construed as being limiting in any way.

Turning now to FIG. 7, an illustrative mobile device 700 and componentsthereof will be described. In some embodiments, the transmitting device116 and/or the receiving device 120 illustrated and described above withreference to FIGS. 1-6 can be configured as and/or can have anarchitecture similar or identical to the mobile device 700 describedherein in FIG. 7. It should be understood, however, that thetransmitting device 116 and/or the receiving device 120 may or may notinclude the functionality described herein with reference to FIG. 7.While connections are not shown between the various componentsillustrated in FIG. 7, it should be understood that some, none, or allof the components illustrated in FIG. 7 can be configured to interactwith one another to carry out various device functions. In someembodiments, the components are arranged so as to communicate via one ormore busses (not shown). Thus, it should be understood that FIG. 7 andthe following description are intended to provide a generalunderstanding of a suitable environment in which various aspects ofembodiments can be implemented, and should not be construed as beinglimiting in any way.

As illustrated in FIG. 7, the mobile device 700 can include a display702 for displaying data. According to various embodiments, the display702 can be configured to display various graphical user interface(“GUI”) elements such as, for example, text, images, video, virtualkeypads and/or keyboards, messaging data, notification messages,metadata, internet content, device status, time, date, calendar data,device preferences, map and location data, combinations thereof, and/orthe like. The mobile device 700 also can include a processor 704 and amemory or other data storage device (“memory”) 706. The processor 704can be configured to process data and/or can execute computer-executableinstructions stored in the memory 706. The computer-executableinstructions executed by the processor 704 can include, for example, anoperating system 708, one or more applications 710 such as the quantumentanglement communication application 118 and/or othercomputer-executable instructions stored in a memory 706, or the like. Insome embodiments, the applications 710 also can include a UI application(not illustrated in FIG. 7).

The UI application can interface with the operating system 708 tofacilitate user interaction with functionality and/or data stored at themobile device 700 and/or stored elsewhere. In some embodiments, theoperating system 708 can include a member of the SYMBIAN OS family ofoperating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILEOS and/or WINDOWS PHONE OS families of operating systems from MICROSOFTCORPORATION, a member of the PALM WEBOS family of operating systems fromHEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family ofoperating systems from RESEARCH IN MOTION LIMITED, a member of the IOSfamily of operating systems from APPLE INC., a member of the ANDROID OSfamily of operating systems from GOOGLE INC., and/or other operatingsystems. These operating systems are merely illustrative of somecontemplated operating systems that may be used in accordance withvarious embodiments of the concepts and technologies described hereinand therefore should not be construed as being limiting in any way.

The UI application can be executed by the processor 704 to aid a user inentering content, configuring settings, manipulating address bookcontent and/or settings, multimode interaction, interacting with otherapplications 710, and otherwise facilitating user interaction with theoperating system 708, the applications 710, and/or other types orinstances of data 712 that can be stored at the mobile device 700. Thedata 712 can include, for example, the token 124, the data 128, the dataaccess request 130, the measurement data 132, and/or other information.According to various embodiments, the data 712 can include, for example,presence applications, visual voice mail applications, messagingapplications, text-to-speech and speech-to-text applications, add-ons,plug-ins, email applications, music applications, video applications,camera applications, location-based service applications, powerconservation applications, game applications, productivity applications,entertainment applications, enterprise applications, combinationsthereof, and the like. The applications 710, the data 712, and/orportions thereof can be stored in the memory 706 and/or in a firmware714, and can be executed by the processor 704.

It can be appreciated that, at least by virtue of storage of theinstructions corresponding to the applications 710 and/or otherinstructions embodying other functionality illustrated and describedherein in the memory 706, and/or by virtue of the instructionscorresponding to the applications 710 and/or other instructionsembodying other functionality illustrated and described herein beingaccessed and/or executed by the processor 704, the mobile device 700 isa special-purpose mobile device that can facilitate providing thefunctionality illustrated and described herein. The firmware 714 alsocan store code for execution during device power up and power downoperations. It can be appreciated that the firmware 714 can be stored ina volatile or non-volatile data storage device including, but notlimited to, the memory 706 and/or a portion thereof.

The mobile device 700 also can include an input/output (“I/O”) interface716. The I/O interface 716 can be configured to support the input/outputof data such as location information, user information, organizationinformation, presence status information, user IDs, passwords, andapplication initiation (start-up) requests. In some embodiments, the I/Ointerface 716 can include a hardwire connection such as a universalserial bus (“USB”) port, a mini-USB port, a micro-USB port, an audiojack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, aparallel port, an Ethernet (RJ45 or RJ48) port, a telephone (RJ11 or thelike) port, a proprietary port, combinations thereof, or the like. Insome embodiments, the mobile device 700 can be configured to synchronizewith another device to transfer content to and/or from the mobile device700. In some embodiments, the mobile device 700 can be configured toreceive updates to one or more of the applications 710 via the I/Ointerface 716, though this is not necessarily the case. In someembodiments, the I/O interface 716 accepts I/O devices such askeyboards, keypads, mice, interface tethers, printers, plotters,external storage, touch/multi-touch screens, touch pads, trackballs,joysticks, microphones, remote control devices, displays, projectors,medical equipment (e.g., stethoscopes, heart monitors, and other healthmetric monitors), modems, routers, external power sources, dockingstations, combinations thereof, and the like. It should be appreciatedthat the I/O interface 716 may be used for communications between themobile device 700 and a network device or local device.

The mobile device 700 also can include a communications component 718.The communications component 718 can be configured to interface with theprocessor 704 to facilitate wired and/or wireless communications withone or more networks such as the network 104 described herein. In someembodiments, other networks include networks that utilize non-cellularwireless technologies such as WI-FI or WIMAX. In some embodiments, thecommunications component 718 includes a multimode communicationssubsystem for facilitating communications via the cellular network andone or more other networks.

The communications component 718, in some embodiments, includes one ormore transceivers. The one or more transceivers, if included, can beconfigured to communicate over the same and/or different wirelesstechnology standards with respect to one another. For example, in someembodiments one or more of the transceivers of the communicationscomponent 718 may be configured to communicate using GSM, CDMAONE,CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greatergeneration technology standards. Moreover, the communications component718 may facilitate communications over various channel access methods(which may or may not be used by the aforementioned standards)including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and thelike.

In addition, the communications component 718 may facilitate datacommunications using GPRS, EDGE, the HSPA protocol family includingHSDPA, EUL or otherwise termed HSDPA, HSPA+, and various other currentand future wireless data access standards. In the illustratedembodiment, the communications component 718 can include a firsttransceiver (“TxRx”) 720A that can operate in a first communicationsmode (e.g., GSM). The communications component 718 also can include anN^(th) transceiver (“TxRx”) 720N that can operate in a secondcommunications mode relative to the first transceiver 720A (e.g., UMTS).While two transceivers 720A-N (hereinafter collectively and/orgenerically referred to as “transceivers 720”) are shown in FIG. 7, itshould be appreciated that less than two, two, and/or more than twotransceivers 720 can be included in the communications component 718.

The communications component 718 also can include an alternativetransceiver (“Alt TxRx”) 722 for supporting other types and/or standardsof communications. According to various contemplated embodiments, thealternative transceiver 722 can communicate using various communicationstechnologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared,infrared data association (“IRDA”), near field communications (“NFC”),other RF technologies, combinations thereof, and the like. In someembodiments, the communications component 718 also can facilitatereception from terrestrial radio networks, digital satellite radionetworks, internet-based radio service networks, combinations thereof,and the like. The communications component 718 can process data from anetwork such as the Internet, an intranet, a broadband network, a WI-FIhotspot, an Internet service provider (“ISP”), a digital subscriber line(“DSL”) provider, a broadband provider, combinations thereof, or thelike.

The mobile device 700 also can include one or more sensors 724. Thesensors 724 can include temperature sensors, light sensors, air qualitysensors, movement sensors, orientation sensors, noise sensors, proximitysensors, or the like. As such, it should be understood that the sensors724 can include, but are not limited to, accelerometers, magnetometers,gyroscopes, infrared sensors, noise sensors, microphones, combinationsthereof, or the like. Additionally, audio capabilities for the mobiledevice 700 may be provided by an audio I/O component 726. The audio I/Ocomponent 726 of the mobile device 700 can include one or more speakersfor the output of audio signals, one or more microphones for thecollection and/or input of audio signals, and/or other audio inputand/or output devices.

The illustrated mobile device 700 also can include a subscriber identitymodule (“SIM”) system 728. The SIM system 728 can include a universalSIM (“USIM”), a universal integrated circuit card (“UICC”) and/or otheridentity devices. The SIM system 728 can include and/or can be connectedto or inserted into an interface such as a slot interface 730. In someembodiments, the slot interface 730 can be configured to acceptinsertion of other identity cards or modules for accessing various typesof networks. Additionally, or alternatively, the slot interface 730 canbe configured to accept multiple subscriber identity cards. Becauseother devices and/or modules for identifying users and/or the mobiledevice 700 are contemplated, it should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

The mobile device 700 also can include an image capture and processingsystem 732 (“image system”). The image system 732 can be configured tocapture or otherwise obtain photos, videos, and/or other visualinformation. As such, the image system 732 can include cameras, lenses,charge-coupled devices (“CCDs”), combinations thereof, or the like. Themobile device 700 may also include a video system 734. The video system734 can be configured to capture, process, record, modify, and/or storevideo content. Photos and videos obtained using the image system 732 andthe video system 734, respectively, may be added as message content toan MMS message, email message, and sent to another mobile device. Thevideo and/or photo content also can be shared with other devices viavarious types of data transfers via wired and/or wireless communicationdevices as described herein.

The mobile device 700 also can include one or more location components736. The location components 736 can be configured to send and/orreceive signals to determine a geographic location of the mobile device700. According to various embodiments, the location components 736 cansend and/or receive signals from global positioning system (“GPS”)devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellularnetwork triangulation data, combinations thereof, and the like. Thelocation component 736 also can be configured to communicate with thecommunications component 718 to retrieve triangulation data fordetermining a location of the mobile device 700. In some embodiments,the location component 736 can interface with cellular network nodes,telephone lines, satellites, location transmitters and/or beacons,wireless network transmitters and receivers, combinations thereof, andthe like. In some embodiments, the location component 736 can includeand/or can communicate with one or more of the sensors 724 such as acompass, an accelerometer, and/or a gyroscope to determine theorientation of the mobile device 700. Using the location component 736,the mobile device 700 can generate and/or receive data to identify itsgeographic location, or to transmit data used by other devices todetermine the location of the mobile device 700. The location component736 may include multiple components for determining the location and/ororientation of the mobile device 700.

The illustrated mobile device 700 also can include a power source 738.The power source 738 can include one or more batteries, power supplies,power cells, and/or other power subsystems including alternating current(“AC”) and/or direct current (“DC”) power devices. The power source 738also can interface with an external power system or charging equipmentvia a power I/O component 740. Because the mobile device 700 can includeadditional and/or alternative components, the above embodiment should beunderstood as being illustrative of one possible operating environmentfor various embodiments of the concepts and technologies describedherein. The described embodiment of the mobile device 700 isillustrative, and should not be construed as being limiting in any way.

As shown in FIG. 7, the mobile device 700 also can include the entangledparticle isolation and measurement hardware 122 illustrated anddescribed herein. As such, it should be understood that the mobiledevice 700 can include a quantum memory, a quantum processor, Hadamardgates, and/or other hardware as illustrated and described herein. Assuch, it can be appreciated that the mobile device 700 can function asthe transmitting device 116 and/or the receiving device 120 in someembodiments. It should be understood that this example is illustrative,and therefore should not be construed as being limiting in any way.

FIG. 8 illustrates an illustrative architecture for a cloud computingplatform 800 that can be capable of executing the software componentsdescribed herein for providing a quantum entanglement communicationservice 106 and/or for interacting with the quantum entanglementcommunication service 106. Thus, it can be appreciated that in someembodiments of the concepts and technologies disclosed herein, the cloudcomputing platform 800 illustrated in FIG. 8 can be used to provide thefunctionality described herein with respect to the server computer 102,the transmitting device 116, the receiving device 120, and/or a devicethat hosts and/or executes the authentication service 126.

The cloud computing platform 800 thus may be utilized to execute anyaspects of the software components presented herein. Thus, according tovarious embodiments of the concepts and technologies disclosed herein,the quantum entanglement communication service 106, the quantumentanglement communication application 118 118, and/or theauthentication service 126 can be implemented, at least in part, on orby elements included in the cloud computing platform 800 illustrated anddescribed herein. Those skilled in the art will appreciate that theillustrated cloud computing platform 800 is a simplification of but onlyone possible implementation of an illustrative cloud computing platform,and as such, the illustrated cloud computing platform 800 should not beconstrued as being limiting in any way.

In the illustrated embodiment, the cloud computing platform 800 caninclude a hardware resource layer 802, a virtualization/control layer804, and a virtual resource layer 806. These layers and/or other layerscan be configured to cooperate with each other and/or other elements ofa cloud computing platform 800 to perform operations as will bedescribed in detail herein. While connections are shown between some ofthe components illustrated in FIG. 8, it should be understood that some,none, or all of the components illustrated in FIG. 8 can be configuredto interact with one another to carry out various functions describedherein. In some embodiments, the components are arranged so as tocommunicate via one or more networks such as, for example, the network104 illustrated and described hereinabove (not shown in FIG. 8). Thus,it should be understood that FIG. 8 and the following description areintended to provide a general understanding of a suitable environment inwhich various aspects of embodiments can be implemented, and should notbe construed as being limiting in any way.

The hardware resource layer 802 can provide hardware resources. In theillustrated embodiment, the hardware resources can include one or morecompute resources 808, one or more memory resources 810, and one or moreother resources 812. The compute resource(s) 808 can include one or morehardware components that can perform computations to process data,and/or to execute computer-executable instructions of one or moreapplication programs, operating systems, services, and/or other softwareillustrated and described herein.

According to various embodiments, the compute resources 808 can includeone or more central processing units (“CPUs”). The CPUs can beconfigured with one or more processing cores. In some embodiments, thecompute resources 808 can include one or more graphics processing units(“GPUs”). The GPUs can be configured to accelerate operations performedby one or more CPUs, and/or to perform computations to process data,and/or to execute computer-executable instructions of one or moreapplication programs, operating systems, and/or other software that mayor may not include instructions that are specifically graphicscomputations and/or related to graphics computations. In someembodiments, the compute resources 808 can include one or more discreteGPUs. In some other embodiments, the compute resources 808 can includeone or more CPU and/or GPU components that can be configured inaccordance with a co-processing CPU/GPU computing model. Thus, it can beappreciated that in some embodiments of the compute resources 808, asequential part of an application can execute on a CPU and acomputationally-intensive part of the application can be accelerated bythe GPU. It should be understood that this example is illustrative, andtherefore should not be construed as being limiting in any way.

In some embodiments, the compute resources 808 also can include one ormore system on a chip (“SoC”) components. It should be understood thatthe an SoC component can operate in association with one or more othercomponents as illustrated and described herein, for example, one or moreof the memory resources 810 and/or one or more of the other resources812. In some embodiments in which an SoC component is included, thecompute resources 808 can be or can include one or more embodiments ofthe SNAPDRAGON brand family of SoCs, available from QUALCOMM of SanDiego, Calif.; one or more embodiment of the TEGRA brand family of SoCs,available from NVIDIA of Santa Clara, Calif.; one or more embodiment ofthe HUMMINGBIRD brand family of SoCs, available from SAMSUNG of Seoul,South Korea; one or more embodiment of the Open Multimedia ApplicationPlatform (“OMAP”) family of SoCs, available from TEXAS INSTRUMENTS ofDallas, Tex.; one or more customized versions of any of the above SoCs;and/or one or more other brand and/or one or more proprietary SoCs.

The compute resources 808 can be or can include one or more hardwarecomponents arranged in accordance with an ARM architecture, availablefor license from ARM HOLDINGS of Cambridge, United Kingdom.Alternatively, the compute resources 808 can be or can include one ormore hardware components arranged in accordance with an x86architecture, such as an architecture available from INTEL CORPORATIONof Mountain View, Calif., and others. Those skilled in the art willappreciate the implementation of the compute resources 808 can utilizevarious computation architectures and/or processing architectures. Assuch, the various example embodiments of the compute resources 808 asmentioned hereinabove should not be construed as being limiting in anyway. Rather, implementations of embodiments of the concepts andtechnologies disclosed herein can be implemented using compute resources808 having any of the particular computation architecture and/orcombination of computation architectures mentioned herein as well asother architectures.

Although not separately illustrated in FIG. 8, it should be understoodthat the compute resources 808 illustrated and described herein can hostand/or execute various services, applications, portals, and/or otherfunctionality illustrated and described herein. Thus, the computeresources 808 can host and/or can execute the quantum entanglementcommunication service 106, the quantum entanglement communicationapplication 118, the authentication service 126, and/or otherapplications or services illustrated and described herein.

The memory resource(s) 810 can include one or more hardware componentsthat can perform or provide storage operations, including temporaryand/or permanent storage operations. In some embodiments, the memoryresource(s) 810 can include volatile and/or non-volatile memoryimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules, orother data disclosed herein. Computer storage media is definedhereinabove and therefore should be understood as including, in variousembodiments, random access memory (“RAM”), read-only memory (“ROM”),Erasable Programmable ROM (“EPROM”), Electrically Erasable ProgrammableROM (“EEPROM”), flash memory or other solid state memory technology,CD-ROM, digital versatile disks (“DVD”), or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedata and that can be accessed by the compute resources 808, subject tothe definition of “computer storage media” provided above (e.g., asexcluding waves and signals per se and/or communication media as definedin this application).

Although not illustrated in FIG. 8, it should be understood that thememory resources 810 can host or store the various data illustrated anddescribed herein including, but not limited to, the request 114, thetoken 124, the data 128, the data access request 130, the measurementdata 132, and/or other data, if desired. It should be understood thatthis example is illustrative, and therefore should not be construed asbeing limiting in any way.

The other resource(s) 812 can include any other hardware resources thatcan be utilized by the compute resources(s) 808 and/or the memoryresource(s) 810 to perform operations. The other resource(s) 812 caninclude one or more input and/or output processors (e.g., a networkinterface controller and/or a wireless radio), one or more modems, oneor more codec chipsets, one or more pipeline processors, one or morefast Fourier transform (“FFT”) processors, one or more digital signalprocessors (“DSPs”), one or more speech synthesizers, combinationsthereof, or the like.

The hardware resources operating within the hardware resource layer 802can be virtualized by one or more virtual machine monitors (“VMMs”)814A-814N (also known as “hypervisors;” hereinafter “VMMs 814”). TheVMMs 814 can operate within the virtualization/control layer 804 tomanage one or more virtual resources that can reside in the virtualresource layer 806. The VMMs 814 can be or can include software,firmware, and/or hardware that alone or in combination with othersoftware, firmware, and/or hardware, can manage one or more virtualresources operating within the virtual resource layer 806.

The virtual resources operating within the virtual resource layer 806can include abstractions of at least a portion of the compute resources808, the memory resources 810, the other resources 812, or anycombination thereof. These abstractions are referred to herein asvirtual machines (“VMs”). In the illustrated embodiment, the virtualresource layer 806 includes VMs 816A-816N (hereinafter “VMs 816”).

Based on the foregoing, it should be appreciated that systems andmethods for a quantum entanglement communication service have beendisclosed herein. Although the subject matter presented herein has beendescribed in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer-readable media, it is to be understood that the conceptsand technologies disclosed herein are not necessarily limited to thespecific features, acts, or media described herein. Rather, the specificfeatures, acts and mediums are disclosed as example forms ofimplementing the concepts and technologies disclosed herein.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments of the concepts and technologies disclosed herein.

1. A system comprising: a first computer comprising a processor; and a memory that stores computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising detecting, at the first computer, a data access request to access data stored at the first computer in response to detecting the data access request, generating, by the first computer, a request comprising a request that a server computer generate an entangled particle pair, wherein the server computer comprises an entangled particle pair generator, receiving, by the first computer, measurement data that corresponds to a measurement observed after interacting a first bit of a token stored at a second computer with a first entangled particle from the entangled particle pair, determining, by the first computer, an operation to perform on a second entangled particle of the entangled particle pair at the first computer, performing, by the first computer, the operation on the second entangled particle, measuring, at the first computer, a state of the second entangled particle, the state comprising a value, and generating, by the first computer, a bit string comprising a number that corresponds to the value.
 2. The system of claim 1, wherein the measurement comprises a value of 00, and the operation on the second entangled particle comprises measuring the state of the second particle.
 3. The system of claim 1, wherein the measurement comprises a value of 01, and the operation on the second entangled particle comprises performing an X gate operation on the second entangled particle.
 4. The system of claim 1, wherein the measurement comprises a value of 10, and the operation on the second entangled particle comprises performing an Z gate operation on the second entangled particle.
 5. The system of claim 1, wherein the measurement comprises a value of 11, and the operation on the second entangled particle comprises performing an X gate operation and a Z gate operation on the second entangled particle.
 6. The system of claim 1, wherein the request specifies endpoints of a communication link over which the data is to be transmitted, wherein the endpoints comprise the first computer and the second computer, and wherein the server computer sends the second entangled particle to the second computer.
 7. The system of claim 1, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising determining if the token comprises another bit, and in response to determining that the token comprises the other bit: receiving another instance of measurement data, wherein the other instance of measurement data comprises another measurement observed after interacting a second bit of the token with a third entangled particle from another entangled particle pair; obtaining a fourth entangled particle; determining another operation to perform on the fourth entangled particle based on the other value; performing the operation on the fourth entangled particle; measuring a state of the fourth entangled particle, the state comprising another value; and adding another number that corresponds to the other value to the bit string.
 8. The system of claim 1, wherein the first computer comprises entangled particle isolation and measurement hardware.
 9. A method comprising: detecting, at a first computer comprising a processor, a data access request to access data stored at the first computer; in response to detecting the data access request, generating, by the processor, a request comprising a request that a server computer generate an entangled particle pair, wherein the server computer comprises an entangled particle pair generator; receiving, by the processor, measurement data that corresponds to a measurement observed after interacting a first bit of a token stored at a second computer with a first entangled particle from the entangled particle pair; determining, by the processor, an operation to perform on a second entangled particle of the entangled particle pair at the first computer; performing, by the processor, the operation on the second entangled particle; measuring, at the first computer, a state of the second entangled particle, the state comprising a value; and generating, by the processor, a bit string comprising a number that corresponds to the value.
 10. The method of claim 9, wherein the measurement comprises a value of 00, and the operation on the second entangled particle comprises measuring the state of the second particle.
 11. The method of claim 9, wherein the measurement comprises a value of 01, and the operation on the second entangled particle comprises performing an X gate operation on the second entangled particle.
 12. The method of claim 9, wherein the measurement comprises a value of 10, and the operation on the second entangled particle comprises performing an Z gate operation on the second entangled particle.
 13. The method of claim 9, wherein the measurement comprises a value of 11, and the operation on the second entangled particle comprises performing an X gate operation and a Z gate operation on the second entangled particle.
 14. The method of claim 9, wherein the request specifies a number of bits in the token, and wherein the request for generation of an entangled particle pair comprises a request to generate the number of entangled particle pairs.
 15. The method of claim 9, wherein the request specifies endpoints of a communication link over which the data is to be transmitted, wherein the endpoints comprise the first computer and the second computer, and wherein the server computer sends the second entangled particle to the second computer.
 16. The method of claim 9, further comprising determining, by the processor, if the token comprises another bit, and in response to determining that the token comprises the other bit: receiving another instance of measurement data, wherein the other instance of measurement data comprises another measurement observed after interacting a second bit of the token with a third entangled particle from another entangled particle pair; obtaining a fourth entangled particle; determining another operation to perform on the fourth entangled particle based on the other value; performing the operation on the fourth entangled particle; measuring a state of the fourth entangled particle, the state comprising another value; and adding another number that corresponds to the other value to the bit string.
 17. The method of claim 9, wherein the first computer comprises entangled particle isolation and measurement hardware.
 18. A computer storage medium having computer-executable instructions stored thereon that, when executed by a processor, cause the processor to perform operations comprising: detecting, at a first computer, a data access request to access data stored at the first computer; in response to detecting the data access request, generating, by the first computer, a request comprising a request that a server computer generate an entangled particle pair, wherein the server computer comprises an entangled particle pair generator; receiving, by the first computer, measurement data that corresponds to a measurement observed after interacting a first bit of a token stored at a second computer with a first entangled particle from the entangled particle pair; determining, by the first computer, an operation to perform on a second entangled particle of the entangled particle pair at the first computer; performing, by the first computer, the operation on the second entangled particle; measuring, at the first computer, a state of the second entangled particle, the state comprising a value; and generating, by the first computer, a bit string comprising a number that corresponds to the value.
 19. The computer storage medium of claim 18, wherein the request specifies endpoints of a communication link over which the data is to be transmitted, wherein the endpoints comprise the first computer and the second computer, and wherein the server computer sends the second entangled particle to the second computer.
 20. The computer storage medium of claim 18, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising determining if the token comprises another bit, and in response to determining that the token comprises the other bit: receiving another instance of measurement data, wherein the other instance of measurement data comprises another measurement observed after interacting a second bit of the token with a third entangled particle from another entangled particle pair; obtaining a fourth entangled particle; determining another operation to perform on the fourth entangled particle based on the other value; performing the operation on the fourth entangled particle; measuring a state of the fourth entangled particle, the state comprising another value; and adding another number that corresponds to the other value to the bit string. 